Sending verification password responsive to mobile device proximity

ABSTRACT

A method includes detecting proximity between a mobile device and a remote device associated with a transaction reserved by a user of the mobile device and a mode of the electronic device. A verification password is sent to the remote device responsive to detecting the proximity and the mode. A device includes a module to detect proximity between the device and a remote device associated with a transaction reserved by a user of the device occurring within a predefined distance threshold and a processor coupled to the module. A device includes another module to detect a stationary mode of the electronic device occurring for at least a predefined duration threshold. The processor is sends a verification password to the remote device responsive to detecting the proximity and the mode.

CROSS REFERENCE TO PRIOR APPLICATIONS

This application is a continuation application claiming priority andbenefit under 35 U.S.C. § 120 from U.S. application Ser. No. 17/159,216,filed Jan. 27, 2021, which is a continuation-in-part applicationclaiming priority and benefit under 35 U.S.C. § 120 from U.S.application Ser. No. 15/993,988, filed May 31, 2018, each of which isincorporated by reference for all purposes. U.S. Ser. No. 15/993,988claims priority to Indian Patent Application Ser. No. 201731022873,filed Jun. 29, 2017.

BACKGROUND Field of the Disclosure

The disclosed subject matter relates generally to mobile computingsystems and, more particularly, to the sending of a verificationpassword responsive to mobile device proximity.

Description of the Related Art

Mobile devices are being increasingly used to handle commercialtransactions without the need for separate credit card or other paymentprocessing. In some instances, verification passwords are employed toprovide an additional level of identity security. For example, a usermay transact for transportation using an application on the mobiledevice. When completing the reservation, the user may be provided with averification password, such as a one-time password (OTP). Upon enteringthe vehicle, the user may orally communicate the verification passwordto the driver, who enters the verification password into a differentmobile device, thereby verifying the identity of the passenger andinitiating the service. Upon completion of the transportation service,the rider is automatically billed in accordance with the previouslyregistered payment arrangements. Thus, the user may reserve and completethe transport service without the need to manage separate paymentarrangements. The use of the verification password provides additionalsecurity for the passenger, as it verifies that the transportationservice was properly handled. One potential inconvenience with the useof verification passwords in this context is that it requires the riderto access the mobile device to retrieve the password, preventing theuser from employing the device for a call or other activity.

Another type of service that may employ a verification password is adelivery service. When a user transacts for a delivery, a verificationpassword is provided. When the delivery is made, the user may providethe verification password to the delivery person, thereby authenticatingthe transaction. This approach also provides additional security forboth the individual ordering the delivery and the delivery vendor, asthe user's identity and delivery location are verified. However, such anapproach may be inconvenient for the user as the mobile device wouldhave to be accessed to search for the authentication password. Thetransaction for the goods being delivered may be conducted hours, days,or even weeks prior to the actual delivery. It may be difficult for theuser to locate the verification password in the mobile device at thetime of delivery. In some instances, the user may have inadvertentlydeleted the message containing the verification password, causingadditional delay and inconvenience for the user, as the delivery servicemay have to be contacted to retrieve the verification password or togenerate a new one.

The present disclosure is directed to various methods and devices thatmay solve or at least reduce some of the problems identified above.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure may be better understood, and its numerousfeatures and advantages made apparent to those skilled in the art byreferencing the accompanying drawings.

FIG. 1 is a simplified block diagram of a mobile device operable forautomatically communicating or displaying verification passwords,according to some embodiments disclosed herein;

FIG. 2 is a simplified flow diagram of a method for communicating averification password based on mobile device proximity, according tosome embodiments disclosed herein;

FIG. 3 is a simplified flow diagram of a method for displaying averification password based on a mode and proximity of an electronicdevice, according to some embodiments disclosed herein;

FIG. 4 is a simplified flow diagram of a method for displaying averification password based on expected appointment time window,according to some embodiments disclosed herein; and

FIG. 5 is a front view of the device of FIG. 1 illustrating an examplenotification list that includes a verification password and expectedservice time, according to some embodiments disclosed herein.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF EMBODIMENT(S)

FIGS. 1-4 illustrate example techniques for automatically processingverification passwords for a user of a mobile device. In someembodiments, device context information such as location, travel mode,proximity to another mobile device, etc. may be employed to verify thatthe user is engaging in a previously contracted point-of-service (POS)transaction associated with a verification password (e.g., a one-timepassword (OTP)). For example, the POS transaction may be associated witha transportation service (e.g., taxi or ride sharing). The use of theverification password helps to ensure both proper service and properbilling. The verification password may be, for instance, required forthe billing process, thereby ensuring an unscrupulous operator does notbill the customer without first providing the service. The verificationpassword may be communicated from the mobile device of the user to aservice provider automatically based on the context information. In someembodiments, the user may contract for a time window transaction havingan associated verification password. For example, a time windowtransaction may include a delivery transaction. The verificationpassword and an expected service completion window may be extracted froma document associated with the time window transaction, and theverification password may be automatically displayed on the mobiledevice proximate the service completion window.

FIG. 1 is a simplistic block diagram of a device 100. The device 100implements a computing system 105 including, among other things, aprocessor 110, a memory 115, a microphone 120, a speaker 125, a display130, a motion sensor 132 (e.g., accelerometer, magnetometer, mercuryswitch, gyroscope, compass, or some combination thereof), a proximitycommunication module 135 (e.g., a radio frequency identification (RFID)module, an ultra wide band (UWB) module, a near field communication(NFC) module, and so forth), and a location module 140 (e.g., globalpositioning system (GPS) module, Wi-Fi location module, etc.). Theproximity communication module 135 can include a combination of sensorsto detect proximity, e.g., a combination of a Wi-Fi module, a Bluetooth®module, and a UWB module, which collectively are referred to as a sensorhub. The use of a combination of sensors can allow for a more granularproximity determination. Thus, in one or more embodiments the proximitycommunication module 135 includes a sensor hub comprising a Bluetooth®module and a Wi-Fi module in combination with a UWB module. Othercombinations of modules suitable for a sensor hub will be obvious tothose of ordinary skill in the art having the benefit of thisdisclosure.

The proximity communication module 135 can, such as when configured as aUWB module, have a range of up to one hundred and fifty meters whileprecisely determining the proximity of another object with the device100 with an accuracy of within thirty centimeters. The memory 115 may bea volatile memory (e.g., DRAM, SRAM) or a non-volatile memory (e.g.,ROM, flash memory, hard disk, etc.). The device 100 includes atransceiver 145 for transmitting and receiving signals via an antenna150 over a communication link. The transceiver 145 may include one ormore radios for communicating according to different radio accesstechnologies, such as cellular, Wi-Fi, Bluetooth®, etc. Thecommunication link may have a variety of forms. In some embodiments, thecommunication link may be a wireless radio or cellular radio link. Thecommunication link may also communicate over a packet-basedcommunication network, such as the Internet. In one embodiment, a cloudcomputing resource 155 may interface with the device 100 to implementone or more of the functions described herein.

In various embodiments, the device 100 may be embodied in a handheld orwearable device, such as a laptop computer, a handheld computer, atablet computer, a mobile device, a telephone, a personal dataassistant, a music player, a game device, a wearable computing deviceand the like. To the extent certain example aspects of the device 100are not described herein, such example aspects may or may not beincluded in various embodiments without limiting the spirit and scope ofthe embodiments of the present application as would be understood by oneof skill in the art.

In the device 100, the processor 110 may execute instructions stored inthe memory 115 and store information in the memory 115, such as theresults of the executed instructions. Some embodiments of the processor110 and the memory 115 may be configured to implement a transactionverification application 160. The transaction verification application160 performs various functions to identify and track verificationpasswords associated with transactions contracted by a user of thedevice 100. The transaction verification application 160 may maintain atransaction list 165 identifying point-of-service (POS) or time windowtransactions contracted by the user of the device 100. The transactionverification application 160 may automatically extract the informationfor the transactions from applications (e.g., a POS application 170 forcontracting transportation services) executed on the device 100,messages received on the device 100 (e.g., email or text), or webdocuments (e.g., web pages) viewed on the device 100.

FIG. 2 is a simplified flow diagram of a method 200 for communicating averification password based on mobile device proximity, according tosome embodiments disclosed herein. In the example illustrated in FIG. 2, the transactions may be POS transactions, such as transportationservices.

In method block 205, the transaction verification application 160extracts transaction information, including a verification password anda transaction location. The transaction verification application 160 maystore the extracted information in the transaction list 165. In someembodiments, the user may execute the POS application 170 to contractfor the POS service. In some embodiments, the transaction verificationapplication 160 may interface with the POS application 170 to receivethe transaction details, or it may be integrated into the POSapplication 170. In some embodiments, the transaction verificationapplication 160 may extract the transaction details from documentsassociated with the transaction. For example, the transaction may becompleted using a web page, or the service provider may send transactiondetails via email or text message. As used herein, the term documentrefers to a web page, email message, or text message received by thedevice 100 associated with the transaction.

In method block 210, the transaction verification application 160detects proximity to a remote device operated by the service provider.In some embodiments, the proximity may be determined using devicecontext information such as the device location information provided bythe location module 140 (see FIG. 1 ). The device location may becompared to the transaction location (e.g., pickup location) todetermine proximity. In some embodiments, the device 100 may communicatewith the service provider device to indicate proximity. For example, thedevice 100 may communicate to the service provider device using UWB,RFID, or NFC communication via the proximity communication module 135(see FIG. 1 ) to determine that the proximity of the device 100 and theremote device operated by the service provider is within a predefineddistance threshold, one example of which is two meters or less. In oneor more embodiments, the predefined distance is one meter for instance.The proximity communication module 135 may, using UWB for example,determine that the device 100 is within a predefined distance threshold,such as two meters, one meter, or less than one meter, while the motionsensor 132 determines that the device 100 has been at a stationarylocation, e.g., not with a user while walking, running, biking, etc.,for at least a predefined duration threshold, such as one minute, thirtyseconds, fifteen seconds, and so forth. The proximity communicationmodule 135 of the device 100 may read a UWB tag, RFID tag, or otherreadable object associated with the service provider device. Theproximity communication may also be linked to the device location,service provider device location, mobile device motion, and transactionlocation in that the transaction verification application 160 maysearch, optionally within a predefined distance threshold, for theservice provider device when the device 100 is in the transactionlocation, and optionally when the device 100 has been stationarilysituated within the transaction for at least a predefined durationthreshold.

In some embodiments, the device 100 may employ additional context datain addition to the location data. As noted above, a combination ofproximity threshold and stationary duration threshold can be used inconjunction with, or separate from, location information. For example,the device 100 may communicate to the service provider device using UWB,RFID, or NFC communication via the proximity communication module 135(see FIG. 1 ) to determine that the proximity of the device 100 and theremote device operated by the service provider is within a predefineddistance threshold, such as two meters or less. The proximitycommunication module 135 can determine that the device 100 is within apredefined distance threshold, such as about one meter, while the motionsensor 132 determines that the device 100 has been stationary withreference to location for at least a predefined duration threshold, suchas one minute, thirty seconds, fifteen seconds, and so forth. These twomeasurements can be used in combination, both in conjunction with, orindependent of, transaction location. In method block 215, thetransaction verification application 160 determines whether contextinformation associated with the device 100 indicates transactionengagement. This additional context information may provide assurancenot only that the user is near the service provider, but that the userhas also engaged in the transaction. This additional context informationmay also provide assurance not only that the user is within a predefineddistance threshold less than two meters, such as one meter, of theservice provider, but also that the user has been stationary at thatlocation for at least a predefined duration threshold, such as thirtyseconds. If only location information were employed, the driver coulddrive off without the passenger and still appear to complete thetransaction.

In one embodiment, the context information includes a motion mode of thedevice 100. For example, the device 100 may identify modes of the device100 such as walking, stationary, driving, etc. The device 100 mayidentify such a mode of the device 100, such as being stationary,occurring for at least a predefined duration of time, such as oneminute, thirty seconds, fifteen seconds, ten seconds, and so forth. Thedevice 100 may use motion data from the motion sensor 132 to determinethe mode. The device 100 may use motion data from the motion sensor 132in conjunction with an onboard clock and/or timer of the processor 110to determine the mode occurring for at least a predefined durationthreshold. The transaction verification application 160 may verify thetransaction engagement in method block 215 based on a transition from awalking mode to a driving mode. The transaction verification application160 may verify the transaction engagement in method block 215 based uponthe device 100 being stationary for at least a predefined durationthreshold.

In one embodiment, the context information includes the device 100 beingsituated within a predefined distance threshold less than two meters,such as one meter, of a service provider device. In addition to, orwithout consideration of, the device 100 and the service provider devicebeing at a common location, the device 100 may employ the proximitycommunication module 135 to detect the device 100 being within thepredefined threshold distance of the service provider device. Thetransaction verification application 160 may verify the transactionengagement in method block 215 based upon the device 100 being withinthe predefined distance threshold.

In one embodiment, the context information includes a noise profile ofthe device 100. For example, the device 100 may monitor the microphone120 (see FIG. 1 ) and compare the current noise profile to a library ofreference noise profiles. For example, the noise profile may match anoutdoors reference profile if the user is outdoors walking to thetransaction location. The noise profile may match a vehicle referenceprofile if the user is in a vehicle (e.g., less ambient noise). Thetransaction verification application 160 may verify the transactionengagement in method block 215 based on a transition from an outdoornoise profile to a vehicle noise profile.

In some embodiments, the transaction verification application 160 mayevaluate the context information in various combinations. For example,in one embodiment the transaction verification application 160 mayevaluate both the motion mode and the noise profile in method block 215.In other embodiments, the transaction verification application 160 mayevaluate both the stationary mode and the distance threshold in methodblock 215. In still other embodiments, the transaction verificationapplication 160 may evaluate the stationary mode for the predefinedduration threshold and the proximity between device and service providerdevice being within the predefined distance threshold in method block215 such that a verification password is only transferred when it isconfirmed that the device 100 and a service provider device are within,say, one meter of each other with the device 100 being stationary atthat location for, say, at least thirty seconds. Other combinations ofcontext information suitable for evaluation in method block 215 will beobvious to those of ordinary skill in the art having the benefit of thisdisclosure.

Upon identifying transaction engagement in method block 215, thetransaction verification application 160 sends the verification passwordto the service provider device in method block 220. The verificationpassword may be sent via text message, by the POS application 170, viapeer-to-peer message, via audio message (e.g., audible or encoded), viainfrared message, etc.

Automatically extracting the verification password and providing it tothe service provided based on device context (e.g., location, motionmode, noise profile, etc.) greatly simplifies the process the useremploys to complete the transaction. The user does not have to interactwith the device 100 to find the verification password or interrupt otheruses of the device 100. When the transaction is engaged, theverification password is automatically communicated to the serviceprovider.

FIG. 3 is a simplified flow diagram of a method 300 for communicating averification password based on mobile device proximity being within apredefined distance threshold of a service provider device while beingstationary for at least a predefined duration threshold, according tosome embodiments disclosed herein. In the example illustrated in FIG. 3, the transactions may be POS transactions, such as transportationservices.

In method block 305, the transaction verification application 160detects that a user of a device 100 is utilizing a service, such as atransportation service or delivery service. In method block 305 thetransaction verification application 160 detects this by detecting thescheduling of a request for service requiring a verification password tobe transmitted to a service provider. Other techniques for thetransaction verification application 160 to detect service utilizationcan be used at method block 305. For example, in some embodiments theuser may execute the POS application 170 to contract for the POSservice. In some embodiments, the transaction verification application160 may interface with the POS application 170 to receive thetransaction details, or it may be integrated into the POS application170. In some embodiments, in method block 305 the transactionverification application 160 can detect that a user is utilizing atransportation service where, on boarding the service providertransportation device, the device 100 will be required to transfer averification password to a service provider device at the serviceprovider transportation device prior to initiation of the servicecommencing. For example, the transaction may be completed using a webpage, or the service provider may send transaction details via email ortext message.

At method block 310, the transaction verification application 160extracts transaction information, as previously described. Thetransaction information can include one or more of a verificationpassword, a predefined duration threshold during which the device 100must be stationary, a predefined distance threshold within which thedevice 100 must be from a service provider device, and a transactionlocation. The transaction verification application 160 may store theextracted information in the transaction list 165. In some embodiments,the transaction verification application 160 may extract the transactiondetails from documents associated with the transaction that are receivedby the device 100 associated with the transaction.

In method block 315, the transaction verification application 160detects proximity to a remote device operated by the service provider.In some embodiments, the proximity may be determined using serviceprovider device context information such as when the service, providerarrives at a transaction location collocated with the device 100 orwithin a predefined distance threshold of the device 100. In methodblock 315, the transaction verification application 160 may also,optionally utilizing the proximity communication module 135, locationmodule 140, and/or motion sensor 132, that the device 100 is approachingthe location of the service provider device and/or that the device 100has reached the location of the service provider device. The proximitymay be determined using device context information such as the devicelocation information provided by the location module 140. The devicelocation may be compared to the transaction location (e.g., pickuplocation) to determine proximity.

In method block 320, the transaction verification application 160,optionally utilizing the proximity communication module 135, detectsthat the device is within a predefined distance threshold, such as onemeter, of the service provider device. In some embodiments, the device100 may communicate with the service provider device to confirmproximity within the predefined distance threshold. For example, thedevice 100 may communicate to the service provider device using UWBcommunication via the proximity communication module 135 to determinethat the proximity of the device 100 and the remote device operated bythe service provider is within a predefined distance threshold.

In method block 325, the transaction verification application 160,optionally utilizing an on-board clock or timer of the processor 110,detects that the device 100 has been stationary for at least apredefined duration threshold, such as thirty seconds, twenty seconds,ten seconds, or another predefined duration threshold. Method block 320and method block 325 can be used in combination. For example, theproximity communication module 135 may use UWB communication todetermine that the device 100 is within the predefined distancethreshold while the motion sensor 132 determines that the device 100 hasbeen at a stationary location for at least the predefined durationthreshold. The use of a combination of the proximity distance thresholdand the stationary duration threshold advantageously utilizes thegranularity of location accuracy offered by the proximity communicationmodule 135, especially when equipped with a UWB module, to solve thesituation of seamlessly delivering a verification password from thedevice 100 to a service provider vice responsive to detecting thisproximity.

The proximity communication may also be linked to the device location,service provider device location, mobile device motion, and transactionlocation in that the transaction verification application 160 maysearch, optionally within a predefined distance threshold, for theservice provider device when the device 100 is in the transactionlocation, and optionally when the device 100 has been stationary withinthe transaction for at least a predefined duration threshold.

In some embodiments, the device 100 may employ additional context datain addition to the location data in optional method block 330. Any ofthe context data described above with reference to the method 200 ofFIG. 2 could be used accordingly, alone or in combination, with themethod 300 of FIG. 3 in optional method block 330. For example, acombination of a motion mode of the device 100 where the device 100transitions from a walking mode to a seated and/or riding mode, and anoise profile of the device 100 where a noise profile matching anoutdoors reference profile transitions to a vehicle reference profilewith less ambient noise may be determined in optional method block 330.The transaction verification application 160 may verify the transactionengagement in optional method block 330 based upon the combination ofcontext data considered.

In method block 335, the transaction verification application 160 sendsthe verification password to the service provider device. Theverification password may be sent via text message, by the POSapplication 170, via peer-to-peer message, via audio message (e.g.,audible or encoded), via infrared message, etc. Automatically extractingthe verification password and providing it to the service provided basedon device context (e.g., being within a predefined distance threshold ofa service provider device and having been stationary for a predefinedduration threshold, etc.) greatly simplifies the process the useremploys to complete the transaction. The user does not have to interactwith the device 100 to find the verification password or interrupt otheruses of the device 100. When the transaction is engaged, theverification password is automatically communicated to the serviceprovider.

FIG. 4 is a simplified flow diagram of a method 400 for retrieving averification password based on expected appointment time window,according to some embodiments disclosed herein. In the exampleillustrated in FIG. 4 , the transactions may be time transactions, suchas delivery services.

In method block 405, the transaction verification application 160extracts transaction information, including a verification password anda service time. The transaction verification application 160 may storethe extracted information in the transaction list 165. In someembodiments, the transaction verification application 160 may extractthe transaction details from documents associated with the transaction.For example, the transaction may be completed using a web page, or theservice provider may send transaction details via email or text message.As used herein, the term document refers to a web page, email message,or text message received by the device 100 associated with thetransaction.

In some embodiments, the transaction verification application 160 mayupdate the expected service time based on new information received inthe device 100 (e.g., text message, emails, etc.) indicating a moreaccurate service time, a change to the service time, etc.

In method block 410, the transaction verification application 160determines that the current time is proximate the service time. Forexample, transaction verification application 160 may determine that thecurrent time is within a particular time window relative to the expectedservice time. The size of the time window may depend on the informationextracted regarding the transaction. If the service provider indicatesonly a particular day for the service, the time window may be theassociated day. If a more refined time window is provided, a shortertime window may be employed. The time window may also be updated basedon updates provided by the service provider on the service time.

The transaction verification application 160 provides the verificationpassword on the display 130 in method block 415 responsive to detectingservice time proximity in method block 410. In some embodiments, thetransaction verification application 160 may send a notification messageto the user.

FIG. 5 is a front view of the device 100 of FIG. 1 illustrating anexample notification list 500. The notification list 500 includes theverification password 505 and the expected service time 510. Thenotification list 500 may also include additional notificationinformation, such as recent messages, calls, mail, etc. The notificationlist 500 may be provided in a low power AoD state, where the device 100is locked and full functionality is not present. In such a state, thefunctionality of the device 100 may be limited (e.g., receiving calls ormessages, and providing status information on the display 130). The usersimply has to look at the display during the service time window or whenthe delivery arrives to see the verification password. The user does nothave to unlock the device 100 or search for the transaction to retrievethe verification password. In some embodiments, the notification listincluding the verification password may also be provided in afully-active mode of the device 100.

Providing the verification password on the display 130 proximate theservice time greatly simplifies the process the user employs to completethe transaction. The user does not have to interact with the device 100to find the verification password or other details of the transaction.When the appropriate time period arrives, the user is provided with theassociated verification password.

A method provided detects proximity between a mobile device and a remotedevice associated with a transaction reserved by a user of the mobiledevice, detects a stationary mode of the mobile device at a locationwhere proximity between the mobile device and the remote device isdetected, extracts a verification password from a document on the mobiledevice associated with the transaction, and sends the verificationpassword to the remote device responsive to detecting both the proximityand the stationary mode.

A device provided includes a first module detecting proximity betweenthe device and a remote device associated with a transaction reserved bya user of the device, a second module detecting a stationary mode of thedevice, and a processor operable with the first module and the secondmodule, wherein the processor extracts a verification passwordassociated with the transaction from a document associated with thetransaction stored on the mobile device and sends the verificationpassword to the remote device responsive to detecting the proximity andthe stationary mode.

Another method provided detects proximity between a mobile device and aremote device associated with a transaction reserved by a user of themobile device occurring within a predefined distance threshold, detectsa stationary mode of the mobile device occurring for at least apredefined duration threshold at a location where proximity between themobile device and the remote device is detected, and sends averification password to the remote device responsive to detecting theproximity occurring within the predefined distance threshold and thestationary mode occurring for at least the predefined duration thresholdat the location.

In some embodiments, certain aspects of the techniques described abovemay be implemented by one or more processors of a processing systemexecuting software. The techniques described herein may be implementedby executing software on a computing device, such as the processor 110of FIG. 1 , however, such methods are not abstract in that they improvethe operation of the device 100 and the user's experience when operatingthe device 100. Prior to execution, the software instructions may betransferred from a non-transitory computer readable storage medium to amemory, such as the memory 115 of FIG. 1 .

The software may include one or more sets of executable instructionsstored or otherwise tangibly embodied on a non-transitory computerreadable storage medium. The software can include the instructions andcertain data that, when executed by one or more processors, manipulatethe one or more processors to perform one or more aspects of thetechniques described above. The non-transitory computer readable storagemedium can include, for example, a magnetic or optical disk storagedevice, solid state storage devices such as Flash memory, a cache,random access memory (RAM) or other non-volatile memory device ordevices, and the like. The executable instructions stored on thenon-transitory computer readable storage medium may be in source code,assembly language code, object code, or other instruction format that isinterpreted or otherwise executable by one or more processors.

A computer readable storage medium may include any storage medium, orcombination of storage media, accessible by a computer system during useto provide instructions and/or data to the computer system. Such storagemedia can include, but is not limited to, optical media (e.g., compactdisc (CD), digital versatile disc (DVD), Blu-Ray disc), magnetic media(e.g., floppy disc, magnetic tape or magnetic hard drive), volatilememory (e.g., random access memory (RAM) or cache), non-volatile memory(e.g., read-only memory (ROM) or Flash memory), ormicroelectromechanical systems (MEMS)-based storage media. The computerreadable storage medium may be embedded in the computing system (e.g.,system RAM or ROM), fixedly attached to the computing system (e.g., amagnetic hard drive), removably attached to the computing system (e.g.,an optical disc or Universal Serial Bus (USB)-based Flash memory), orcoupled to the computer system via a wired or wireless network (e.g.,network accessible storage (NAS)).

The particular embodiments disclosed above are illustrative only, as theinvention may be modified and practiced in different but equivalentmanners apparent to those skilled in the art having the benefit of theteachings herein. For example, the process steps set forth above may beperformed in a different order. Furthermore, no limitations are intendedto the details of construction or design herein shown, other than asdescribed in the claims below. It is therefore evident that theparticular embodiments disclosed above may be altered or modified andall such variations are considered within the scope and spirit of theinvention. Note that the use of terms, such as “first,” “second,”“third” or “fourth” to describe various processes or structures in thisspecification and in the attached claims is only used as a shorthandreference to such steps/structures and does not necessarily imply thatsuch steps/structures are performed/formed in that ordered sequence. Ofcourse, depending upon the exact claim language, an ordered sequence ofsuch processes may or may not be required. Accordingly, the protectionsought herein is as set forth in the claims below.

What is claimed is:
 1. A method, comprising: detecting proximity betweena mobile device and a remote device associated with a transactionreserved by a user of the mobile device; detecting a stationary mode ofthe mobile device at a location where proximity between the mobiledevice and the remote device is detected; and sending a verificationpassword to the remote device responsive to detecting both the proximityand the stationary mode.
 2. The method of claim 1, wherein the detectingthe proximity comprises detecting the proximity between the mobiledevice and the remote device being within a distance threshold.
 3. Themethod of claim 2, wherein the detecting the stationary mode comprisesdetecting the stationary mode occurring for at least a durationthreshold.
 4. The method of claim 3, wherein the sending theverification password to the remote device occurs only when theproximity is within the distance threshold and the stationary modeoccurs for at least the duration threshold.
 5. The method of claim 4,wherein the distance threshold is two meters or less.
 6. The method ofclaim 1, wherein detecting the proximity further comprises: detecting afirst location of the mobile device; receiving a second locationassociated with the transaction in the mobile device; and comparing thefirst and second locations to determine the first location is collocatedwith the second location.
 7. The method of claim 1, wherein detectingthe proximity further comprises detecting context information associatedwith the mobile device indicative of transaction engagement.
 8. Themethod of claim 7, wherein detecting the context information comprisesdetecting a transition between a walking mode of the mobile device andthe stationary mode of the mobile device.
 9. The method of claim 7,wherein detecting the context information further comprises: monitoringa current noise profile of the mobile device; and comparing the currentnoise profile to at least one reference noise profile associated withthe transaction.
 10. The method of claim 1, wherein the verificationpassword comprises one of a web document, a text message, or an emailmessage.
 11. A device, comprising: a first module detecting proximitybetween the device and a remote device associated with a transactionreserved by a user of the device; a second module detecting a stationarymode of the device; and a processor operable with the first module andthe second module, wherein the processor sends a verification passwordto the remote device responsive to detecting the proximity and thestationary mode.
 12. The device of claim 11, the first module detectingthe proximity between the device and the remote device being within adistance threshold.
 13. The device of claim 12, the second moduledetecting the stationary mode of the device occurring for at least aduration threshold.
 14. The device of claim 13, further comprising athird module detecting a location of the device, wherein the processordetects location associated with the transaction to determine thestationary mode occurs at the location associated with the transaction.15. The device of claim 11, wherein the first module comprises aproximity communication module communicating with the remote device todetermine proximity to the remote device.
 16. The device of claim 15,the proximity communication module comprising an ultra wide band (UWB)module.
 17. The device of claim 11, wherein the processor detectscontext information associated with the device indicative of transactionengagement and sends the verification password to the remote devicefurther responsive to the context information.
 18. A method, comprising:detecting proximity between a mobile device and a remote deviceassociated with a transaction reserved by a user of the mobile device;detecting a stationary mode of the mobile device occurring at a locationwhere proximity between the mobile device and the remote device isdetected; and sending a verification password to the remote deviceresponsive to detecting the proximity and the stationary mode occurring.19. The method of claim 18, further comprising detecting contextinformation associated with the mobile device indicative of transactionengagement by detecting a transition between a walking mode of themobile device and a stationary mode of the mobile device.
 20. The methodof claim 18, wherein the sending comprises sending a text message.